Automated workflow access based on clinical user role and location

ABSTRACT

Systems, methods, computer-readable media for automating displays based on admissions, transfers, and discharges are provided. In embodiments, a location associated with a clinician is detected. A role associated with the clinician authenticated to a first device is determined. One or more applications associated with the clinician based on the location and the role is automatically launched on the first device. In embodiments, authentication requests from the clinician are received for a second device. A session associated with the one or more applications is suspended on the first device and resumed on the second device.

CROSS-REFERENCE TO RELATED APPLICATION

This application is a continuation of U.S. Nonprovisional patentapplication Ser. No. 15/836,554, entitled “Automatic Workflow AccessBased On User Role And Location” and filed on Dec. 8, 2017, which is acontinuation of U.S. Pat. No. 9,858,630, entitled “Automatic WorkflowAccess Based On User Role And Location” and filed Sep. 28, 2012, whichare incorporated by reference herein, in their entireties.

BACKGROUND

Patient medical information, such as that contained in a medical record,allows health care providers to provide continuity of care to patients.It is critical for clinicians providing care to patients to review andupdate each patient's medical record. The growth in access to andutilization of electronic medical records by healthcare providers andfacilities has significantly reduced the time and organization effortsrequired by paper medical records. Unfortunately, this growth hasintroduced new problems. Medical records associated with the incorrectpatient are often mistakenly viewed without knowledge by the clinician.

Exacerbating this problem further, clinicians are constantly on themove. For example, clinicians are responsible for patients in multiplehealthcare facilities or multiple areas within a single healthcarefacility. Each area or each facility may have different softwareapplications or different components within an application supportingvarious aspects of the clinicians working in those areas or facilities.While making rounds, clinicians are constantly required to login todifferent devices and applications or change views from within anapplication to perform their duties. Time spent logging intoapplications, navigating to the appropriate view or area within anapplication, and then locating the correct records can adversely impactany efficiency gained by utilizing electronic medical records.

SUMMARY

This summary is provided to introduce a selection of concepts in asimplified form that are further described below in the DetailedDescription. This summary is not intended to identify key features oressential features of the claimed subject matter, nor is it intended tobe used as an aid in determining the scope of the claimed subjectmatter.

Embodiments of the present invention relate to methods, systems, andcomputer readable media for automating workflows based on user roles andlocations. Accordingly, in one embodiment, computer storage media havingcomputer-executable instructions embodied thereon that, when executed,facilitate a method of automating workflow access based on user role andlocation. A location associated with a clinician in a healthcarefacility is detected. A role associated with the clinician authenticatedwith a first device is determined. One or more applications associatedwith the clinician based on the location and the role is automaticallylaunched on the first device.

In another embodiment, a computer system, comprising a processor coupledto a computer storage medium, the computer storage medium having storedthereon a plurality of computer software components executable by theprocessor, for automating workflows based on user roles and locations isprovided. A detecting component detects a location associated with aclinician in a healthcare facility. A role component determines a roleassociated with the clinician authenticated with a first device. Anapplication component launches, on the first device, one or moreapplications associated with the clinician based on the location and therole. A session component suspends a session associated with the one ormore applications on a first device and resumes the session associatedwith the one or more applications on a second device when the clinicianlogs into the second device.

In one embodiment, computer storage media having computer-executableinstructions embodied thereon that, when executed, facilitate a methodof automating workflow access based on user role and location. A roleassociated with a clinician authenticated to a first device iscommunicated from the first device. A workplace including one or moreapplications associated with the clinician and based on the location andthe role of the clinician is received from a server. The workplace isdisplayed on the first device.

BRIEF DESCRIPTION OF THE DRAWINGS

Embodiments are described in detail below with reference to the attacheddrawing figures, wherein:

FIG. 1 is a block diagram of an exemplary computing environment suitablefor use in implementing embodiments of the present invention;

FIG. 2 is an exemplary system architecture suitable for use inimplementing embodiments of the present invention; and

FIGS. 3-4 are flow diagrams of methods in accordance with embodiments ofthe present invention.

DETAILED DESCRIPTION

The subject matter of the present invention is described withspecificity herein to meet statutory requirements. However, thedescription itself is not intended to limit the scope of this patent.Rather, the inventors have contemplated that the claimed subject mattermight also be embodied in other ways, to include different steps orcombinations of steps similar to the ones described in this document, inconjunction with other present or future technologies.

Having briefly described embodiments of the present invention, anexemplary operating environment suitable for use in implementingembodiments of the present invention is described below.

Referring to the drawings in general, and initially to FIG. 1 inparticular, an exemplary computing system environment, a medicalinformation computing system environment, with which embodiments of thepresent invention may be implemented is illustrated and designatedgenerally as reference numeral 100. It will be understood andappreciated by those of ordinary skill in the art that the illustratedmedical information computing system environment 100 is merely anexample of one suitable computing environment and is not intended tosuggest any limitation as to the scope of use or functionality of theinvention. Neither should the medical information computing systemenvironment 100 be interpreted as having any dependency or requirementrelating to any single component or combination of componentsillustrated therein.

The present invention may be operational with numerous other generalpurpose or special purpose computing system environments orconfigurations. Examples of well-known computing systems, environments,and/or configurations that may be suitable for use with the presentinvention include, by way of example only, personal computers, servercomputers, hand-held or laptop devices, multiprocessor systems,microprocessor-based systems, set top boxes, programmable consumerelectronics, network PCs, minicomputers, mainframe computers,distributed computing environments that include any of theabove-mentioned systems or devices, and the like.

The present invention may be described in the general context ofcomputer-executable instructions, such as program modules, beingexecuted by a computer. Generally, program modules include, but are notlimited to, routines, programs, objects, components, and data structuresthat perform particular tasks or implement particular abstract datatypes. The present invention may also be practiced in distributedcomputing environments where tasks are performed by remote processingdevices that are linked through a communications network. In adistributed computing environment, program modules may be located inassociation with local and/or remote computer storage media including,by way of example only, memory storage devices.

With continued reference to FIG. 1 , the exemplary medical informationcomputing system environment 100 includes a general purpose computingdevice in the form of a control server 102. Components of the controlserver 102 may include, without limitation, a processing unit, internalsystem memory, and a suitable system bus for coupling various systemcomponents, including database cluster 104, with the control server 102.The system bus may be any of several types of bus structures, includinga memory bus or memory controller, a peripheral bus, and a local bus,using any of a variety of bus architectures. By way of example, and notlimitation, such architectures include Industry Standard Architecture(ISA) bus, Micro Channel Architecture (MCA) bus, Enhanced ISA (EISA)bus, Video Electronic Standards Association (VESA) local bus, andPeripheral Component Interconnect (PCI) bus, also known as Mezzaninebus.

The control server 102 typically includes therein, or has access to, avariety of computer-readable media, for instance, database cluster 104.Computer-readable media can be any available media that may be accessedby server 102, and includes volatile and nonvolatile media, as well asremovable and non-removable media. By way of example, and notlimitation, computer-readable media may include computer storage media.Computer storage media may include, without limitation, volatile andnonvolatile media, as well as removable and non-removable mediaimplemented in any method or technology for storage of information, suchas computer-readable instructions, data structures, program modules, orother data. In this regard, computer storage media may include, but isnot limited to, RAM, ROM, EEPROM, flash memory or other memorytechnology, CD-ROM, digital versatile disks (DVDs) or other optical diskstorage, magnetic cassettes, magnetic tape, magnetic disk storage, orother magnetic storage device, or any other medium which can be used tostore the desired information and which may be accessed by the controlserver 102. By way of example, and not limitation, communication mediaincludes wired media such as a wired network or direct-wired connection,and wireless media such as acoustic, RF, infrared, and other wirelessmedia. Combinations of any of the above also may be included within thescope of computer-readable media.

The computer storage media discussed above and illustrated in FIG. 1 ,including database cluster 104, provide storage of computer-readableinstructions, data structures, program modules, and other data for thecontrol server 102. The control server 102 may operate in a computernetwork 106 using logical connections to one or more remote computers108. Remote computers 108 may be located at a variety of locations in amedical or research environment, for example, but not limited to,clinical laboratories (e.g., molecular diagnostic laboratories),hospitals and other inpatient settings, veterinary environments,ambulatory settings, medical billing and financial offices, hospitaladministration settings, home health care environments, and clinicians'offices. Clinicians may include, but are not limited to, a treatingphysician or physicians, specialists such as intensivists, surgeons,radiologists, cardiologists, and oncologists, emergency medicaltechnicians, physicians' assistants, nurse practitioners, nurses,nurses' aides, pharmacists, dieticians, microbiologists, laboratoryexperts, laboratory technologists, genetic counselors, researchers,veterinarians, students, and the like. The remote computers 108 may alsobe physically located in non-traditional medical care environments sothat the entire health care community may be capable of integration onthe network. The remote computers 108 may be personal computers,servers, routers, network PCs, peer devices, other common network nodes,or the like, and may include some or all of the elements described abovein relation to the control server 102. The devices can be personaldigital assistants or other like devices.

Exemplary computer networks 106 may include, without limitation, localarea networks (LANs) and/or wide area networks (WANs). Such networkingenvironments are commonplace in offices, enterprise-wide computernetworks, intranets, and the Internet. When utilized in a WAN networkingenvironment, the control server 102 may include a modem or other meansfor establishing communications over the WAN, such as the Internet. In anetworked environment, program modules or portions thereof may be storedin association with the control server 102, the database cluster 104, orany of the remote computers 108. For example, and not by way oflimitation, various application programs may reside on the memoryassociated with any one or more of the remote computers 108. It will beappreciated by those of ordinary skill in the art that the networkconnections shown are exemplary and other means of establishing acommunications link between the computers (e.g., control server 102 andremote computers 108) may be utilized.

In operation, a clinician may enter commands and information into thecontrol server 102 or convey the commands and information to the controlserver 102 via one or more of the remote computers 108 through inputdevices, such as a keyboard, a pointing device (commonly referred to asa mouse), a trackball, or a touch pad. Other input devices may include,without limitation, microphones, satellite dishes, scanners, or thelike. Commands and information may also be sent directly from a remotehealthcare device to the control server 102. These commands andinformation may include input or a trigger (i.e., a user moving from onelocation to another) from a real-time location system, such as detectioncomponent described herein. In addition to a monitor, the control server102 and/or remote computers 108 may include other peripheral outputdevices, such as speakers and a printer.

Although many other internal components of the control server 102 andthe remote computers 108 are not shown, those of ordinary skill in theart will appreciate that such components and their interconnection arewell known. Accordingly, additional details concerning the internalconstruction of the control server 102 and the remote computers 108 arenot further disclosed herein.

With reference to FIG. 2 , a block diagram is illustrated that shows anexemplary computing system architecture 200 for automating workflowsbased on user role and location. It will be appreciated that thecomputing system architecture 200 shown in FIG. 2 is merely an exampleof one suitable computing system and is not intended as having anydependency or requirement related to any single module/component orcombination of modules/components.

The computing system 200 includes network 202, automated workflow module210, mobile device 230, workstation 240, and information system 250.Although only single instances of the elements are depicted in computingsystem 200, it should be appreciated the many instances of each of theelements are contemplated and within the scope of the invention. Forexample, many mobile devices or workstations can be in communicationwith automated workflow module 210. Similarly, many information systemsassociated with any number of applications may be in communication withautomated workflow module 210. Applications hosted by information system250 include any application that may be utilized by a clinician. Forexample, information system 250 may include applications supportingemail, messaging, browsing, research, electronic medical records,imaging, any healthcare related function, and the like. Informationsystem 250 may also include applications supporting admission,discharge, and transfer systems. Information system 250 may furtherinclude applications supporting location, tracking, and proximitydetection.

Automated workflow module 210 may reside on one or more computingdevices, such as, for example, the control server 102 described abovewith reference to FIG. 1 . By way of example, the control server 102includes a computer processor and may be a server, personal computer,desktop computer, laptop computer, handheld device, mobile device,consumer electronic device, or the like. Automated workflow module 210comprises, in various embodiments, detecting component 212, rolecomponent 214, application component 216, session component 218, patientcomponent 220, and peripheral device component.

Detection component 212 detects a location associated with a clinicianin a healthcare facility. In one embodiment, detection component 212detects location changes associated with the clinician. In oneembodiment, detection component 212 receives location information from aclinician tracking system. For example, healthcare resources such asclinicians, patients, equipment, clinical devices, and the like may betracked via a plurality of sensors in the healthcare environment. Thesensors in the healthcare environment may utilize ultrasound technology,infrared technology, radio-frequency identification technology, nearfield communication (NFC), and the like. Using said technology, thesensors send out signals to clinician identifiers, patient identifiers,item identifiers, clinical device identifiers, or the like. An exemplarysensor system is the Cricket Indoor Location System sponsored by the MITProject Oxygen partnership.

The signals are received by the identifiers and the identifiers respondto the signals. A response from an identifier is received by the sensorsand the sensors are able to recognize and determine the location of theresponding identifier and, thus, are aware of the resources within thehealthcare environment. The respective identifiers associated with theresources may be located, e.g., on the person, on the item, or on thedevice. Exemplary identifiers include badges, wristbands, tags, passivelocation sensors, and the like. The locations of clinicians, patients,equipment, or the like, associated with a responding identifier, ispresented or displayed on the dashboard.

In one embodiment, detection component 212 detects a location associatedwith the clinician by associating a device the clinician is logged intowith the clinician's location. The clinician may log-in to the device inany number of ways, such as by physically entering log-in credentials orscanning credentials associated with a badge into an input device ortouchscreen associated with the device. Or, the clinician may log-in tothe device by proximity detection, such as with a badge.

Once the clinician has logged into automated workflow module 210 in anyof the ways described above, role component 214 determines a roleassociated with the clinician authenticated with a first device. Therole may be determined by roles or rights assigned to the clinician'slogin credentials or to a position or title associated with theclinician. The role may further be influenced by a location of theclinician. The location may be a particular area of a single healthcarefacility or may be a particular healthcare facility among a plurality ofhealthcare facilities. For example, a clinician may have different rolesdepending on the particular unit within the healthcare facility theclinician is located. Or, the clinician may have different rolesdepending on the particular healthcare facility (that may be part of arelated or commonly managed network of healthcare facilities) aclinician is making rounds.

Application component 216 launches, on the first device, one or moreapplications associated with the clinician based on the location and therole. In one embodiment, the applications are part of a workspaceassociated with the clinician. In one embodiment, the applicationsinclude a patient list for a particular location to assist the clinicianworking in that location. In one embodiment, application component 216launches one or more clinical applications when detecting component 212detects the clinician's location is a patient-specific location. Forexample, when the clinician is in a patient-specific location (e.g., apatient's room), the clinician does not need access to all of theapplications associated with the clinician's workspace. Rather thanlaunching non-clinical applications such as applications supportingemail, messaging, or browsing, application component 216 only launchesclinical applications that are relevant to perform the clinician'sduties in that location for the role associated with the clinician asdetermined by role component 214. In another embodiment, applicationcomponent 216 automatically opens an appropriate application or recordwithin an application. For example, when the clinician enters apatient's room, if the clinician does not already have the patient's EMRopen or even an EMR application open, application component 216automatically opens the EMR for that particular patient. In this sense,the application state reflects the appropriate changes due to a changein location, while preserving the application's current sessioninformation.

In another embodiment, application component 216 launches one or morenon-clinical applications when detecting component 212 detects theclinician is in a location where the privacy of a patient or group ofpatients may be violated. In another embodiment, application component216 masks identifying data associated with one or more clinicalapplications so the clinician can continue working with a particularclinician application even when the clinician is not in apatient-specific location or if the clinician is in a location where theprivacy of a patient or group of patients may be violated. For example,a clinician may desire to view or chart within a particular patient'srecord while the clinician is outside the patient's room (e.g., at anurse's station, a shared device, or on a mobile device). In order tonot reveal the patient's identity to someone who may be passing by,detecting component 212 detects the clinician is not inside thepatient's room or in the clinician's private office and masks, partiallymasks, hides, obscures, or otherwise removes any identifyinginformation.

Session component 218 suspends a session associated with the one or moreapplications on a first device and resumes the session associated withthe one or more applications on a second device when the clinician logsinto or authenticates with the second device. For example, as aclinician walks into a patient's room, the clinician may be reviewing,on a mobile device, a record associated with the patient (e.g.,patient's electronic medical record (EMR), laboratory results, image,etc.). Once the clinician is inside the patient's room, the clinicianmay desire to log into or authenticate with a workstation or otherdevice in the patient's room. As the clinician logs into orauthenticates with that workstation or other device, session componentsuspends the session on the mobile device and then resumes the sessionon the workstation or other device. For clarity, the session refers to astate within a particular application. For example, the clinician abovemay have a particular application open on the clinician's mobile device.The clinician may have even navigated to a particular item or viewwithin that application. Rather than simply closing the application onthe mobile device and reopening the application on the workstation orother device (or closing the application on the mobile device and thenhaving to reopening the application within the clinician's workspace)and then navigating to that particular item or view, session component218 allows the clinician to essentially pick up where that clinicianleft off within that application while on the mobile device.

In one embodiment, session component 218 suspends a session with the oneor more applications on a first device and resumes the session on asecond device with one or more applications associated with the seconddevice. In other words, session component 218 resumes the session forthe clinician on the second device but only with applicationsappropriate for the second device or a location associated with thesecond device. Applications which are not included in the resumedsession on the first device are suspended until the clinician logs intoanother device or is in a location where those applications are needed.

In one embodiment, session component 218 suspends a session on a firstdevice utilizing at least one first device native application andresumes the session on a second device utilizing at least one seconddevice native application. For example, a clinician may be accessing apatient's chart on a session on a first device. The first device may bean iPad and the chart may be opened on a native iOS application. If theclinician log into a second device in the patient's room that is runninganother operating system, such as a version of Microsoft Windows, thesession is suspended on the first device and resumed on the seconddevice, but with the patient's chart opened in a Microsoft Windows®based EMR application to enable a smooth workflow for the clinician.

In one embodiment, patient component 220 detects a patient associatedwith the location. Patient component 220 may receive patient locationinformation from an admission, discharge, and transfer system thatassociates a patient with a location based on admissions, discharges,and transfers. Or, patient component 220 may receive patient locationfrom a tracking system such as the one described herein with respect todetecting component 212.

In one embodiment, peripheral device component 222 automaticallypopulates a list of available peripheral devices associated with thesecond device. For example, an application may include a print functionor some other function that requires the use of a peripheral device. Theperipheral device may be directly connected to the second device orconnected via a network. Each device within a healthcare facility may beassociated with different peripheral devices depending on a locationwithin the healthcare facility. Rather than a clinician's sessionresuming on a second device with peripheral device information from aprevious device, peripheral device component 222 automatically updatesthe resumed session (and each application included therein) with theperipheral device information that is normally associated with thesecond device. This allows, for example, the clinician to print an imageor other information to the printer normally utilized by the seconddevice without having to manually configure or select the appropriateprinter.

Referring now to FIG. 3 , a flow diagram depicts an illustrative method300 of automating workflow access based on user role and location, inaccordance with an embodiment of the present invention. Initially, atstep 310 a location associated with a clinician in a healthcare facilityis detected. A role associated with the clinician authenticated with afirst device is determined at step 320. One or more applicationsassociated with the clinician based on the location and the role isautomatically launched, at step 330, on the first device.

In one embodiment, the location is a non-patient-specific location. Forexample, the location may be an office associated with the clinician, ashared workstation utilized by clinical staff, a mobile device, and thelike. In this example, a clinician may desire to access applicationsunrelated to a patient. In one embodiment, the one or more applicationsare non-clinical applications associated with the location. For example,the clinician may desire access to email, messaging, browserapplications, and the like. When a non-patient-specific location isdetected, these non-clinical applications may be included in a workspaceassociated with the clinician. Further, depending on the particularnon-patient-specific location, clinical applications may or may not beincluded in the clinician's workspace. For example, a clinician maydesire to work on clinical applications while in the clinician's office,but due to privacy concerns may not desire to work on clinicalapplications while on a shared device, in an area accessible tonon-medical personnel or non-healthcare facility staff, or on a mobiledevice. In some of these instances, the clinician may desire to work onclinical applications, but only if patient identifying data is hidden ormasked as described above. In various embodiments, the type ofapplications included in the clinician's workspace is determined by alocation and a role associated with a clinician, as well as preferencesof the clinician or protocols defined by the particular healthcarefacility or as otherwise required.

In one embodiment, the location is a patient-specific location. Thepatient-specific location may include a patient's room. In oneembodiment, the one or more applications are clinical applicationsassociated with the patient-specific location. For example, theapplications included in a clinician's workspace when a patient-specificlocation is detected may include applications related to patient care,such as applications associated with a patient's EMR. Further, theclinician may not have a need for non-clinical applications and thesemay be excluded from the clinician's workspace in this context.

In one embodiment, an authentication request is received from theclinician for a second device in the healthcare facility. For example,the clinician may be utilizing a mobile device while making rounds. Asthe clinician enters a patient's room, the clinician may log into orauthenticate with a second device, such as an anchor device that isassociated with the patient's room. In a another example, the clinicianmay currently be authenticated with an anchor device in a patient'sroom, and as the clinician leaves the patient's room, the clinician isautomatically logged out of the anchor device and reauthenticated withthe mobile device. Similarly, the clinician may encounter a sharedworkstation, such as at a nurse's station, or a workstation in theclinician's office. The clinician may login to or authenticate with oneof those devices.

In one embodiment, after the authentication request is received for thesecond device, a session associated with the one or more applications onthe first device is suspended. As described above, the session refers toa state of or a placeholder within an application. For example, if aclinician is working within a particular application (e.g., editing datawithin a particular field of a patient's EMR or viewing a particulararea of an image), when the authentication request is received for thesecond device, that particular state of the application (i.e., thesession) is suspended. In one embodiment, the session associated withthe one or more applications is resumed on the second device. Whateverstate the application or applications were in on the first device areautomatically resumed on the second device as if the clinician neverswitched devices. So, if the clinician were updating a particular fieldof a patient's EMR or viewing a particular area of an image when theclinician authenticates with the second device, the state of thoseapplications are resumed on the second device so the clinician cancontinue updating that particular field of the patient's EMR or viewingthat particular area of the image. In other words, the clinician'sworkspace opens up in the same state, at the same point within anapplication or applications as it was on the first device (except forperipheral device information which, in one embodiment, is automaticallyupdated to include the appropriate peripheral device information for thesecond device).

Referring now to FIG. 4 , a flow diagram depicts an illustrative method400 of automating workflow access based on user role and location, inaccordance with an embodiment of the present invention. Initially, atstep 410, a role associated with a clinician authenticated to a firstdevice is communicated from the first device. The role may be determinedby roles or rights assigned to the clinician's login credentials or to aposition or title associated with the clinician. The role may further beinfluenced by a location of the clinician. The location may be aparticular area of a single healthcare facility or may be a particularhealthcare facility among a plurality of healthcare facilities. Forexample, a clinician may have different roles depending on theparticular unit within the healthcare facility the clinician is located.Or, the clinician may have different roles depending on the particularhealthcare facility (that may be part of a related or commonly managednetwork of healthcare facilities) a clinician is making rounds.

At step 420, a workplace including one or more applications associatedwith the clinician and based on a location and role of the clinician arereceived from a server. The applications may be clinical or non-clinicalas described above. Particular functionality or display of theapplications may similarly be influenced by the location and role of theclinician. For example, some components of a particular application maybe important to one role or location but not another. Accordingly, thecomponents or functionality of a particular application may be limitedor enhanced based on these considerations. This increases the efficiencyassociated with the computing infrastructure of the healthcare facilityby providing applications or portions of applications only as needed ordesired. The workplace is displayed on the first device at step 420.

In one embodiment, an indication is received that a second devicereceived an authentication request from the clinician. The requestsignals to the server that the clinician desires to switch devices. Inone embodiment, a session associated with the workspace on the firstdevice is suspended. This allows the clinician to view the clinician'sworkspace in the same state, at the same point within an application orapplications as it was on the first device when the session is resumedon the second device. In one embodiment, the workplace and session(i.e., session information) is communicated to the second device. Eventhough the session is resumed in the same state as it was on the firstdevice, the workplace may include or exclude applications depending onwhat is appropriate for that location and the role associated with theclinician or for the particular device. For example, the clinician maybe viewing the patient's EMR on a mobile device and also have an emailapplication open. Although both applications are suspended, it would notbe appropriate to include the email application in a workspace that isdisplayed on a particular device type or a particular location, such asan anchor device in a patient's room. Accordingly, only the patient'sEMR is included in the workplace (and any other relevant clinicalapplications). In one embodiment, the session includes peripheral deviceinformation associated with the second device.

In one embodiment, an indication is received that the first devicereceived an authentication request. As described above, this can occurautomatically when a clinician exits a patient's room or is no longerproximate to a second device. In one embodiment, the workplace andsession information is communicated to the first device. Continuing theabove example, once the clinician transitions back to the mobile device,the email application is resumed in the clinician's workplace in thesame state prior to transitioning from the mobile device to the anchordevice.

Many different arrangements of the various components depicted, as wellas components not shown, are possible without departing from the scopeof the claims below. Embodiments of our technology have been describedwith the intent to be illustrative rather than restrictive. Alternativeembodiments will become apparent to readers of this disclosure after andbecause of reading it. Alternative means of implementing theaforementioned can be completed without departing from the scope of theclaims below. Certain features and subcombinations are of utility andmay be employed without reference to other features and subcombinationsand are contemplated within the scope of the claims.

The invention claimed is:
 1. A method comprising: causing a computerizedworkspace for a particular user to be generated for display on acomputing device at a physical location, wherein the computerizedworkspace includes an application that is specific to a role of theparticular user and the physical location of the computing device;receiving an indication when the computerized workspace for theparticular user is initiated on another computing device at anotherphysical location; determining a particular graphical user interface ofthe application is displayed at the computing device at the physicallocation; causing the computing device at the physical location to stopthe application in the computerized workspace based on the indicationreceived; determining that the other physical location is associatedwith a privacy risk to the privacy of a patient; and causing theparticular graphical user interface of the application to be generatedfor display in the computerized workspace on the other computing deviceat the other physical location with identifying information of thepatient masked.
 2. The method of claim 1, wherein causing the particulargraphical user interface of the application to be generated for displayin the computerized workspace on the other computing device at the otherphysical location includes automatically navigating to the particulargraphical user interface of the application.
 3. The method of claim 1,further comprising: determining that the other physical location isoutside of a room of the patient or a private office of the clinician todetermine that the other physical location is associated with theprivacy risk; and when causing the particular graphical user interfaceof the application to be generated for display in the computerizedworkspace on the other computing device at the other physical locationwith the identifying information of the patient masked, masking theidentifying information by at least partially obscuring patientidentifying information from the particular graphical user interface toprevent display on the other computing device.
 4. The method of claim 1,further comprising: determining that the other physical location isoutside of a room of the patient or a private office of the clinician todetermine that the other physical location is associated with theprivacy risk; and when causing the particular graphical user interfaceof the application to be generated for display in the computerizedworkspace on the other computing device at the other physical locationwith the identifying information of the patient masked, masking theidentifying information by at least partially removing patientidentifying information from the particular graphical user interface toprevent display on the other computing device.
 5. The method of claim 1,further comprising: determining that the other physical location isoutside of a room of the patient or a private office of the clinician todetermine that the other physical location is associated with theprivacy risk; and when causing the particular graphical user interfaceof the application to be generated for display in the computerizedworkspace on the other computing device at the other physical locationwith the identifying information of the patient masked, masking theidentifying information by at least partially hiding patient identifyinginformation from the particular graphical user interface to preventdisplay on the other computing device.
 6. The method of claim 1, whereinthe other computing device utilizes a different operating system thanthe computing device, and wherein causing the particular graphical userinterface of the application to be generated for display in thecomputerized workspace on the other computing device at the otherphysical location includes automatically navigating to the particulargraphical user interface of the application as run by the differentoperating system.
 7. The method of claim 1, wherein one or more of thecomputing device or the other computing device is a mobile computingdevice, wherein causing the particular graphical user interface of theapplication to be generated for display in the computerized workspace onthe other computing device at the other physical location includesautomatically navigating to the particular graphical user interface ofthe application as run in a mobile view.
 8. One or more non-transitorycomputer storage media devices having computer-executable instructionsembodied thereon for performing a method when executed by one or moreprocessors, the media comprising: causing a computerized workspace for aparticular user to be generated for display on a computing device at aphysical location, wherein the computerized workspace includes anapplication that is specific to a role of the particular user and thephysical location of the computing device; receiving an indication whenthe computerized workspace for the particular user is initiated onanother computing device at another physical location; determining aparticular graphical user interface of the application is displayed atthe computing device at the physical location; causing the computingdevice at the physical location to stop the application in thecomputerized workspace based on the indication received; determiningthat the other computing device is associated with a privacy risk to theprivacy of a patient; and causing the particular graphical userinterface of the application to be generated for display in thecomputerized workspace on the other computing device at the otherphysical location with identifying information of the patient masked. 9.The media of claim 8, further comprises: determining the particulargraphical user interface of the application that is displayed at thecomputing device at the physical location is associated with anelectronic record; and wherein causing the particular graphical userinterface of the application to be generated for display in thecomputerized workspace on the other computing device at the otherphysical location includes automatically loading information from theelectronic record into the particular graphical user interface of theapplication.
 10. The media of claim 8, further comprising: determiningthat the other computing device is associated with the privacy risk bydetermining that the other computing device is shared by multiple users;and in response to determining the other computing device is shared bymultiple users, masking the identifying information by at leastpartially obscuring patient identifying information from the particulargraphical user interface to prevent display on the other computingdevice when causing the particular graphical user interface of theapplication to be generated for display in the computerized workspace onthe other computing device at the other physical location.
 11. The mediaof claim 8, further comprising: determining that the other computingdevice is associated with the privacy risk by determining that the othercomputing device is shared by multiple users; and in response todetermining the other computing device is shared by multiple users,masking the identifying information by at least partially removingpatient identifying information from the particular graphical userinterface to prevent display on the other computing device when causingthe particular graphical user interface of the application to begenerated for display in the computerized workspace on the othercomputing device at the other physical location.
 12. The media of claim8, further comprising: determining that the other computing device isassociated with the privacy risk by determining that the other computingdevice is shared by multiple users; and in response to determining theother computing device is shared by multiple users, masking theidentifying information by at least partially hiding patient identifyinginformation from the particular graphical user interface to preventdisplay on the other computing device when causing the particulargraphical user interface of the application to be generated for displayin the computerized workspace on the other computing device at the otherphysical location.
 13. The media of claim 8, wherein the other computingdevice utilizes a different operating system than the computing device,and wherein causing the particular graphical user interface of theapplication to be generated for display in the computerized workspace onthe other computing device at the other physical location includescausing an automatic navigation to the particular graphical userinterface of the application as run by the different operating system.14. The media of claim 8, wherein one or more of the computing device orthe other computing device is a mobile computing device, wherein causingthe particular graphical user interface of the application to begenerated for display in the computerized workspace on the othercomputing device at the other physical location includes causing anautomatic navigation to the particular graphical user interface of theapplication as run in a mobile view.
 15. A system comprising: one ormore processors configured to: cause a computerized workspace for aparticular user to be generated for display on a computing device at aphysical location, wherein the computerized workspace includes anapplication that is specific to a role of the particular user and thephysical location of the computing device; receive an indication whenthe computerized workspace for the particular user is initiated onanother computing device at another physical location; determine aparticular graphical user interface of the application 1 s displayed atthe computing device at the physical location; cause the computingdevice at the physical location to stop the application in thecomputerized workspace based on the indication received; determiningthat the other physical location is associated with a privacy risk tothe privacy of a patient; and cause the particular graphical userinterface of the application to be generated for display in thecomputerized workspace on the other computing device at the otherphysical location with identifying information of the patient masked.16. The system of claim 15, wherein causing the particular graphicaluser interface of the application to be generated for display in thecomputerized workspace on the other computing device at the otherphysical location includes automatically navigating to the particulargraphical user interface of the application.
 17. The system of claim 15,further comprising: determining that the other physical location isoutside of a room of the patient to determine that the other physicallocation is associated with the privacy risk; and when causing theparticular graphical user interface of the application to be generatedfor display in the computerized workspace on the other computing deviceat the other physical location with the identifying information of thepatient masked, masking the identifying information by at leastpartially obscuring patient identifying information from the particulargraphical user interface to prevent display on the other computingdevice.
 18. The system of claim 15, further comprising: determining thatthe other physical location is outside of a private office of theclinician to determine that the other physical location is associatedwith the privacy risk; and when causing the particular graphical userinterface of the application to be generated for display in thecomputerized workspace on the other computing device at the otherphysical location with the identifying information of the patientmasked, masking the identifying information by at least partiallyremoving patient identifying information from the particular graphicaluser interface to prevent display on the other computing device.
 19. Thesystem of claim 15, further comprising: determining that the otherphysical location is outside of a room of the patient or a privateoffice of the clinician to determine that the other physical location isassociated with the privacy risk; and when causing the particulargraphical user interface of the application to be generated for displayin the computerized workspace on the other computing device at the otherphysical location with the identifying information of the patientmasked, masking the identifying information by at least partially hidingpatient identifying information from the particular graphical userinterface to prevent display on the other computing device.
 20. Thesystem of claim 15, wherein the other computing device utilizes adifferent operating system than the computing device, and whereincausing the particular graphical user interface of the application to begenerated for display in the computerized workspace on the othercomputing device at the other physical location includes automaticallynavigating to the particular graphical user interface of the applicationas run by the different operating system.